http://bill.welliver.org//space/smartos/poste.io upgrade<i class="ital">Note:</i> Verified 3/10/2020<p class="paragraph"/> Updating an LX zone from an updated docker image is pretty simple; if you want to preserve data you'll need to do so before-hand, or have pre-configured your zone to store things in a delegated dataset, which will be preserved across reprovisions. The only real trick is that the reprovision will remove the init script we added to mount the delegated dataset and lofs-mount any directories into the filesystem. So, we'll make sure we put that back in, after the reprovision but before the zone is started back up.<p class="paragraph"/> This procedure also makes a backup of the zone just in case things go badly.<p class="paragraph"/> <i class="ital">Note:</i> though this is presented in the form of a shell script, <b class="bold">DO NOT</b> run it as such, but rather consider each line individually. Otherwise you'll likely trash your zone.<p class="paragraph"/> <div class="code"><pre><pre> <font color=brown># import the new version of the image we want to run </font>imgadm <b><font color=darkblue>import</font></b> analogic/poste.io <font color=brown># make note of the image uuid imported and set NEW_IMAGE to this value </font>UUID=91854c5c-a285-6522-9da8-e38a04116fd6 NEW_IMAGE=some_uuid BACKUP_LOCATION=/zones/images/smtp-data.zfs SNAPSHOT_NAME=begin<p class="paragraph"/> <font color=brown># stop the zone and make a copy of the zfs delegated setup script </font>vmadm stop ${UUID} cp /zones/${UUID}/root/etc/cont-init.d/01-init-zfs.sh /tmp<p class="paragraph"/> <font color=brown># this is not strictly necessary, but sometimes it's nice to have a backup. </font>echo <i><font color=darkred>"Backing up to $BACKUP_LOCATION..."</font></i> zfs snap zones/${UUID}/data@${SNAPSHOT_NAME} zfs send -Recv zones/${UUID}/data@begin &gt; $BACKUP_LOCATION<p class="paragraph"/> echo <i><font color=darkred>"Reprovisioning..."</font></i> echo '{<i><font color=darkred>"image_uuid"</font></i>: <i><font color=darkred>"${NEW_IMAGE}"</font></i>}' | vmadm reprovision ${UUID}<p class="paragraph"/> <font color=brown># restore the zfs delegated dataset bootstrap and truncated directory setup </font><font color=brown># scripts back into place. this is because they have to run the first time, every </font><font color=brown># time and thus can't be installed from /data/_override (which is a feature that </font><font color=brown># poste.io provides for making customizations to their image, and which is not </font><font color=brown># a standard feature across docker images). </font><font color=brown># </font><font color=brown># alternatively, we could override the docker:cmd field and do something there </font><font color=brown># or build a custom docker image. </font>vmadm stop ${UUID} cp /tmp/0*.sh /zones/${UUID}/root/etc/cont-init.d/<p class="paragraph"/> <font color=brown>#If, for some reason the container starts up immediately after provision, the zfs init script won't work as </font><font color=brown>#the /data directory will be present and non-empty. If this happens, move it out of the way and restart. </font><font color=brown># then, zlogin and verify that the /data directory has the delegated dataset (with the local and _override directories) </font> vmadm start ${UUID} <font color=brown># to restart with ipf running we have to reboot. </font>vmadm reboot ${UUID}<p class="paragraph"/> <font color=brown># restoring the delegated dataset is not necessary when we use reprovision, but is </font><font color=brown># kept as an example of how to do it. </font>zfs recv -F zones/${UUID}/data &lt; ${BACKUP_LOCATION} zfs rollback zones/${UUID}/data@${SNAPSHOT_NAME} zfs destroy zones/${UUID}/data@${SNAPSHOT_NAME}<p class="paragraph"/> rm ${BACKUP_LOCATION} </pre></pre></div> Fins 0.9.7http://blogs.law.harvard.edu/tech/rss